Nested View Tool

A Nested View is a container that shows another CygNet Studio screen. That means you can show a screen within a screen. The Nested View can show data from the same Site.Service and Facility as the parent view or it can have unique properties. The file path for a nested view can be the standard file system or the BLOB file system.

You can have as many nested views as you want in one CygNet Studio screen. However, nested views can go only two levels deep.

A Nested View object can be configured to overwrite properties of the screen it is showing. These include the screen’s background color, engineering units, and scroll bars. If the [BackgroundColorMode] property of the Nested View object is set to 1 - Selected, the color specified by the BackColor property is used. If ScrollbarOverride is set to an option other than 1 - No Override, then scroll bar display might be affected. If [UseViewUnits] is set to 1 - Yes, the [Units] property of the parent view will be applied to the nested view. Another property that deals with view units is the AllowUnitsChange property. If set to 1 - Yes, users can change the view units of the nested view in Run mode.

The [ReceiveCustomEvents] property enables automatic forwarding of custom events to the Nested View object.

The Nested View Tool is an ActiveX control. As such, a Nested Tool object has an ActiveX page on the Property Sheet. Many of these properties are the object’s formatting properties. Values for the ActiveX Properties can be set directly on the ActiveX page or in the OCX Properties dialog box, which is accessed by clicking the (OCXProperties) property. See Nested View Tool - ActiveX Properties for more information.

The Nested View Tool has an EventHyperLinkSys event, which is run immediately after EventHyperLink whenever a HyperLink is requested by the nested view.

The Nested View Tool has an EventVersionNotifty event, which is used to periodically check the version of a nested screen against the master file stored in the BLOB file system. See Setting Periodic Version Checks for more information.

Note: Changes made to logging settings in the Client Settings dialog box will not be forwarded to CygNet Studio’s nested views, but command-line parameters will. See Command-Line Logging for more information.